This is required because we use [email protected] in dev to run jest, which uses ESM. Jest can only run CJS by default.

Since graphql-request is ESM, we need to run it through babel-jest:

• transformIgnorePatterns is used to tell Jest to transform graphql-request in node_modules (node_modules are ignored by default)
• transform tells Jest to run babel-jest on .js files in graphql-request to turn ESM to CJS

graphql-request@6 uses cross-fetch, whilst graphql-request@7 uses native fetch (undici)
undici is built in a way that nock@14 and below does not support (support is coming in nock v15)

So, for tests to work, we need to pass a fetch function that nock supports, because mockGraphQLServer from @graphql-codegen/testing is using [email protected]

Hi @dotansimha , @jasonkuhrt,

For [email protected]:
I observe [email protected] doesn't work with graphql@15 because of the way it uses OperationTypeNode:

I'm thinking we could update graphql-request@7 package to drop graphql@15 as peerDep, but looks like graffle is under development, so don't know what the effort to release v7.1.3 is ? Or whther it's possible? 🤔

For this plugin:
This hack is a bit gross but I couldn't find a quick way to stop testing graphql@15 just for this plugin. One way I could think of is to split the test command to have control over which packages to test, and split graphql-request CLI into another CI step.

Keen to hear if you have preferences or ideas!

Hey @eddeee888 I could make a release to do what you are suggesting by easily. We have a branch called legacy for just this kind of reason.

Do you want to make a PR to it and we can discuss further?

Ah good to know about the legacy branch! I think I can make a PR to that branch tonight

Yay, new graphql-request version works. Hack removed. I can live with my conscience 😆

Thank you!

Happy it worked out!